Blue Prism 6.10.1: March 2021

Issues introduced in Blue Prism 6.10 when saving processes no longer occur in environments in which the Blue Prism SQL database is accessed using an SQL account set up with only the minimum recommended access roles. Previously in this scenario, saving a new or existing process in Process Studio and then moving to a different tab resulted in an SQL exception error and the Blue Prism interactive client closing. This issue occurred because the Blue Prism SQL database roles were incorrectly not expanded to accommodate a database schema change implemented in 6.10.0.

The correct permissions are now applied during installation and upgrade of the Blue Prism SQL database.

6.10.0 deployments that have applied the database script available via Customer Support to address this issue do not require any additional configuration when upgrading to 6.10.1.

A primary key constraint intermittent error no longer occurs when using auto-initialization to trigger a Blue Prism business object that is exposed as a web service. Previously, the error resulted in the session not being created and the object actions not being executed.

To improve performance in Control Room and to improve behavior when creating or starting multiple sessions at the same time, the way in which session event requests are sent from the interactive client to runtime resources and the frequency of subsequent Control Room refreshes have been updated as follows:

• Create and update session requests triggered from within Control Room now occur in a background thread to minimize the impact on the user interface.

• When create, start, or delete session requests need to be sent to multiple runtime resources, the requests are sent to each runtime resource sequentially. Once a request has been sent to one resource, further requests will only be sent to a subsequent resource when the first has been acknowledged or if 5 seconds have passed – whichever occurs first.

• When create or start session event requests need to be sent to a large number of runtime resources, these are now separated into batches of up to 50 requests. Additionally, a Control Room refresh will only be triggered when each batch of session events has been completed. Previously in Blue Prism 6.10.0, a Control Room refresh was incorrectly triggered by each individual session event. This was most noticeable when creating, starting, or deleting multiple sessions at the same time, which potentially caused performance issues in environments with a high level of session-related activity.

When debugging a process or object, clicking the Evaluate Expression button for a stage that references a collection no longer incorrectly returns an Object reference not set to an instance of an object error.

An issue has been fixed where the database conversion from a single-authentication Active Directory environment to a multi-authentication Active Directory environment failed if the rootDSE of the Active Directory forest did not have the global catalog role enabled.

Previously, the conversion process attempted to query the rootDSE to obtain the Secure Identifiers (SIDs) of the Blue Prism users to be converted. If the rootDSE did not have the global catalog role enabled, it returned blank identifiers which caused the conversion to fail and the database was restored to its previous state.

The conversion process now searches the Active Directory forest for a global catalog in order to identify the SIDs of the users.

The tracking ID functionality introduced in Blue Prism 6.9 can now be used in conjunction with the IsConnected read action when automating Chrome, Edge, and Firefox browser applications. By using the tracking ID as an input parameter in the IsConnected read action, Blue Prism can identify whether or not it is still connected to web pages associated with the tracking ID.

An issue has been fixed where Blue Prism incorrectly appeared to be attached to a Chrome browser application after it had been detached, which prevented Blue Prism from reattaching to it. The detach action now successfully triggers the disconnect event and the IsConnected property of the browser application is correctly set to 'false', allowing Blue Prism to successfully detect when a browser application has been detached from Blue Prism. The attach action can only be used if the Use fixed browser extension port (31924) only system setting is enabled.

When launching a browser page from Blue Prism using the Browser-based Application (Chrome, Firefox, or Edge Chromium) mode, the browser extension status and version number are now detected when the extension is launched instead of when the web page completes loading. This fixes an issue where a timeout error occurred when launching a web page that required HTTP basic authentication.